Release 10.1A: OpenEdge Development:
Progress Dynamics Advanced Development

Customization tables

A full discussion of the Progress Dynamics support for customization is beyond the scope of this document, but because the customization tables affect the use of the other object tables, it is important to understand what the customization tables are and how they are used to modify objects at run time.

Customization support allows the developer to define types of end-user specifics that should affect the appearance or behavior of the application at run time. This might include changes based on the user ID, the client display platform, the task the user is doing, or anything else that can be categorized. Customization basically means that certain attribute values can be changed for an object depending on how it is used and who uses it.

There are three tables that provide support for customization:

The ryc_customization_type table defines different categories of customization that are supported.
The ryc_customization_result table stores specific result code values for a given customization type.
The rym_customization table acts as a kind of cross-reference table that can be used to provide a more complex mapping between types and codes when no direct mapping is possible or practical.

Figure 8–17 is an excerpt from the database model and shows the three customization tables and how they relate to the SmartObject table.

Figure 8–17: Customization tables